Payment Initiation APIs 4.0

(0 reviews)

Sandbox Mocking Information - Error Scenarios

To invoke the APIs, a developer needs to download Test Data by registering and logging into the BOI Developer Portal. This Test Data will provide the required PSU/Customer Account details required to invoke the APIs.

This sections provides Sandbox Mocking Information related to API requests and responses.

1.1. Domestic Payment Consents & Domestic Scheduled Payment Consents
ValidationsDescription/Response
AmountValidationIf Amount is of the form 100xx consent status is RJCT
CurrencyValidationAllowed Currencies are EUR, GBP else consent status is RJCT
POST API ValidationIf Amount is of the form 800xx, API will return 500, Internal Server Error
GET API ValidationIf Amount is of the form 700xx, Consent will be created but on fetching status user will get Internal Server Error
SecondaryIdentification Validation If SecondaryIdentification of CreditorAccount provided in the request is of the form 333xx, API will return 400 Bad Request with "U022" error.
1.2. Domestic Payment– Confirmation of Funds API
ValidationsDescription/Response
AmountValidation If Amount is of the form 200xx then fundsAvailable flag in response is false else true.
AdditionalValidation If Amount is of the form 600xx API returns 500, Internal Server Error.
1.3. Domestic Standing Order Consents API
ValidationsDescription/Response
AmountValidationIf FirstPaymentAmount value is of the form 100xx consent status is RJCT
CurrencyValidationAllowed Currencies are EUR, GBP else consent status is RJCT
POST API ValidationIf FirstPaymentAmount value is of the form 800xx, API will return 500, Internal Server Error
GET API ValidationIf FirstPaymentAmount value is of the form 700xx, Consent will be created but on fetching status user will get Internal Server Error
SecondaryIdentification Validation If SecondaryIdentification of CreditorAccount provided in the request is of the form 333xx, API will return 400 Bad Request with "U022" error.
1.4. Domestic Payments API
ValidationsDescription/Response
AmountValidation If Amount is of the form 20[1–9], followed by optionally a decimal with up to 2 digits after it, payment status is "RCVD".
If Amount is of the form 200xx, followed by up to 10 digits, and optionally a decimal with up to 5 digits after it, payment status is "RJCT".
If Amount is of the form 26[1-9], followed by optionally a decimal with up to 2 digits after it, payment status is "ACSP".
If Amount is of the form 27[1-9], followed by optionally a decimal with up to 2 digits after it, payment status is "ACSC".
MultiAuthValidation If Amount is of the form 300xx, MultiAuth status is "AUTH" and Payment status is "ACSP".
If Amount is of the form 30[1–9], followed by optionally a decimal with up to 2 digits after it, MultiAuth status is "AWAF" and Payment status is "PATC".
If Amount is of the form 500xx, MultiAuth status is "RJCT" and Payment Status is "RJCT".
POST API Validation If Amount is of the form 600xx, API will return 500, Internal Server Error.
GET API Validation If Amount is of the form 700xx, payments resource will be created but on fetching status user will get Internal Server Error.
AfterCutOffDateException If Amount is of the form 900xx, API will return 400 Bad Request with "U012" error.
1.5. Domestic Scheduled Payments API
ValidationsDescription/Response
AmountValidation If Amount is of the form 20[1–9], followed by optionally a decimal with up to 2 digits after it, payment status is "RCVD".
If Amount is of the form 200xx, followed by up to 10 digits, and optionally a decimal with up to 5 digits after it, payment status is "RJCT".
If Amount is of the form 26[1-9], followed by optionally a decimal with up to 2 digits after it, payment status is "ACSP".
MultiAuthValidation If Amount is of the form 300xx, MultiAuth status is "AUTH" and Payment status is "ACSP".
If Amount is of the form 30[1–9], followed by optionally a decimal with up to 2 digits after it, MultiAuth status is "AWAF" and Payment status is "PATC".
If Amount is of the form 500xx, MultiAuth status is "RJCT" and Payment Status is "RJCT".
POST API Validation If Amount is of the form 600xx, API will return 500, Internal Server Error.
GET API Validation If Amount is of the form 700xx, payments resource will be created but on fetching status user will get Internal Server Error.
AfterCutOffDateException If Amount is of the form 900xx, API will return 400 Bad Request with "U012" .
1.6. Domestic Standing Orders API
ValidationsDescription/Response
AmountValidation If FirstPaymentAmount value is of the form 20[1–9], followed by optionally a decimal with up to 2 digits after it, payment status is "RCVD".
If FirstPaymentAmount value is of the form 25[1–9], followed by optionally a decimal with up to 2 digits after it, payment status is "INFA".
MultiAuthValidation If FirstPaymentAmount value is of the form 26[1–9], followed by optionally a decimal with up to 2 digits after it, payment status is "INCO".
POST API Validation If FirstPaymentAmount value is of the form 600xx, API will return 500, Internal Server Error.
GET API Validation If FirstPaymentAmount value is of the form 700xx, payments resource will be created but on fetching status user will get Internal Server Error.
AfterCutOffDateException If FirstPaymentAmount value is of the form 900xx, API will return 400 Bad Request with "U012" error.

Reviews